ftp.cs.arizona.edu/ftp.cs.arizona.edu.tar/ftp.cs.arizona.edu/icon/newsgrp/group99a.txt/000008_icon-group-sender _Tue Jan 26 08:08:57 1999.msg

Internet Message Format | 2000-09-20 | 2KB

Return-Path: <icon-group-sender>
Received: (from root@localhost)
    by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) id IAA19953
    for icon-group-addresses; Tue, 26 Jan 1999 08:06:21 -0700 (MST)
Message-Id: <[e-mail]>
Date: Mon, 25 Jan 1999 21:23:22 -0800
From: Jim Mehl <[e-mail]>
X-Accept-Language: en
To: [e-mail]
Subject: Re: qei questions
Errors-To: [e-mail]
Status: RO

  It sounds like Dianna is having the same problem I was having a
couple of weeks ago. Thanks to help from Steve Wampler, I was able
to sort it out.
  Dianna didn't say, but I assume she is using the Windows version
of Icon.
  The problem is that qei (like a lot of other programs in the Icon
library) makes a call to system("icont ...) to invoke the Icon
compiler to evaluate expressions. Unfortunately with the Windows
version, the Icon compiler is named wicont (for the windowing
version) or nticont (for the command line version).
  The way I solved this was to make a copy of the nticont.exe
compiler named icont.exe. From a Windows DOS command line issue
     copy nticont.exe icont.exe
     patchstr icont.exe icont.exe
Patchstr comes with Windows Icon and is described under
Windows Icon Help -> Known Bugs and Limitations.
It is also necessary to compile qei.icn with either nticont or the
icont you just created. What you get is a command line only version
of qei, but it's better than nothing.
  It might be helpful if the documentation for Windows Icon mentioned
the fact that the library includes all sorts of calls to icont, but
that no icont.exe is included.

Jim Mehl
Los Gatos, CA
[e-mail]